-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: support module-definition plugin #835
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: liyanfang <[email protected]>
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #835 +/- ##
==========================================
- Coverage 60.91% 58.91% -2.01%
==========================================
Files 109 114 +5
Lines 19375 19819 +444
==========================================
- Hits 11803 11676 -127
- Misses 6104 6703 +599
+ Partials 1468 1440 -28
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's some implementation problems, but before that, can you show the screenshots for what this plugin looks like?
Signed-off-by: liyanfang <[email protected]>
Signed-off-by: liyanfang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like you are providing a framework user can continue to develop a kind of plugin, which will override the specified definition properties form?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like you are providing a framework user can continue to develop a kind of plugin, which will override the specified definition properties form?
Yes, user can write plugin to override component\trait\policy\workflow-step properties form |
I have seen lot's of duplicated code of the "definition" plugin and original plugin. We can implement that by add some fields to that. |
Signed-off-by: liyanfang <[email protected]>
Point 2, Do you mean commit the code of topology-policy plugin as a demo plugin ? |
Signed-off-by: liyanfang <[email protected]>
Signed-off-by: liyanfang <[email protected]>
I mean you can attach the implementation at introductio and seems you have done that. |
Signed-off-by: liyanfang <[email protected]>
Signed-off-by: liyanfang <[email protected]>
Signed-off-by: liyanfang <[email protected]>
Signed-off-by: liyanfang <[email protected]>
Description of your changes
support definition plugin
we can write a module-definition plugin and enabled
and then we can see it override the default module-definition properties editor form
the plugin implementation demo is to reference https://github.com/mujinhuakai/velaux-plugin-topology/tree/main
Fixes #
I have:
yarn lint
to ensure the frontend changes are ready for review.make reviewable
to ensure the server changes are ready for review.backport release-x.y
labels to auto-backport this PR if necessary.Special notes for your reviewer